Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 27dd5da04e6ed9cfbcf34eb3b692cec2ba51927988f80f2bc8d799b125886014

Tx prefix hash: 9b4fbc10bb82adca29557e3de482cc3171d96ea98a1652a536931b5c66b972bd
Tx public key: c7f4fba15677fdabb3e49461ffd0abbe659d06875aff1e3caf61458e2d3536e3
Timestamp: 1725955081 Timestamp [UCT]: 2024-09-10 07:58:01 Age [y:d:h:m:s]: 00:247:16:38:10
Block: 1106934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176879 RingCT/type: yes/0
Extra: 01c7f4fba15677fdabb3e49461ffd0abbe659d06875aff1e3caf61458e2d3536e3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b10e0963f7aae1b816967f07d3c3e9ac7910ab2e2930071a82ef96882133b6a 0.600000000000 1584537 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1106944, "vin": [ { "gen": { "height": 1106934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b10e0963f7aae1b816967f07d3c3e9ac7910ab2e2930071a82ef96882133b6a" } } ], "extra": [ 1, 199, 244, 251, 161, 86, 119, 253, 171, 179, 228, 148, 97, 255, 208, 171, 190, 101, 157, 6, 135, 90, 255, 30, 60, 175, 97, 69, 142, 45, 53, 54, 227, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8