Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4175c5483f68836d414adf3d65c7de5060557e82ae4905b51b2079af54c2c3

Tx prefix hash: b5953a5e73b593b942a952c3fbc8a2deac15fd5abb5f975c95cf27c1690647d0
Tx public key: 51afb70ff9d61ca3a38985c7bb8594019f6d85e771cc2c55036fb94b6def3612
Timestamp: 1709858850 Timestamp [UCT]: 2024-03-08 00:47:30 Age [y:d:h:m:s]: 01:029:23:58:03
Block: 973493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282417 RingCT/type: yes/0
Extra: 0151afb70ff9d61ca3a38985c7bb8594019f6d85e771cc2c55036fb94b6def361202110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c62f4a7a30189c69adc24cd4e99cafb034328dc98938cb3833533935a23fcf 0.600000000000 1433428 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": 973503, "vin": [ { "gen": { "height": 973493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c62f4a7a30189c69adc24cd4e99cafb034328dc98938cb3833533935a23fcf" } } ], "extra": [ 1, 81, 175, 183, 15, 249, 214, 28, 163, 163, 137, 133, 199, 187, 133, 148, 1, 159, 109, 133, 231, 113, 204, 44, 85, 3, 111, 185, 75, 109, 239, 54, 18, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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