Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6433228d5789a21a3366f597e7310309568c655f734cfb558f6766c4a93d221c

Tx prefix hash: de12e5ff3d3a1ec6a69f561466fa94d010e2c99c2132f153269965a6fbbeed43
Tx public key: 51cb4e0d184f2137ad8e57f7db6788711433c3cb521ab3e2df8d7381d220d2e1
Timestamp: 1711756381 Timestamp [UCT]: 2024-03-29 23:53:01 Age [y:d:h:m:s]: 01:011:22:56:52
Block: 989232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269487 RingCT/type: yes/0
Extra: 0151cb4e0d184f2137ad8e57f7db6788711433c3cb521ab3e2df8d7381d220d2e102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a2cfb7711e8b5ce0ac6270f4de5fd1b06371552c739ab6401ef2a56ee1658bf 0.600000000000 1449527 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": 989242, "vin": [ { "gen": { "height": 989232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2cfb7711e8b5ce0ac6270f4de5fd1b06371552c739ab6401ef2a56ee1658bf" } } ], "extra": [ 1, 81, 203, 78, 13, 24, 79, 33, 55, 173, 142, 87, 247, 219, 103, 136, 113, 20, 51, 195, 203, 82, 26, 179, 226, 223, 141, 115, 129, 210, 32, 210, 225, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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