Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d4d362dfb2bca5249ae00b173f94cec9cafa13994c6eb21aa5d2a5f930e9aa3

Tx prefix hash: 11614f5cf766eff8abffcb02d364460962e992af299d5a75cbb55fea75ce56c3
Tx public key: 65062401bfe2204d979c8168182613f952f10ce51a34de111b3171b45b95b9e8
Timestamp: 1719062812 Timestamp [UCT]: 2024-06-22 13:26:52 Age [y:d:h:m:s]: 01:140:23:18:02
Block: 1049769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359320 RingCT/type: yes/0
Extra: 0165062401bfe2204d979c8168182613f952f10ce51a34de111b3171b45b95b9e802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b72dd2acf5a0561ad33e7008d31a8a8ebd465a674999e1fb5be414a261a51f 0.600000000000 1519874 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": 1049779, "vin": [ { "gen": { "height": 1049769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b72dd2acf5a0561ad33e7008d31a8a8ebd465a674999e1fb5be414a261a51f" } } ], "extra": [ 1, 101, 6, 36, 1, 191, 226, 32, 77, 151, 156, 129, 104, 24, 38, 19, 249, 82, 241, 12, 229, 26, 52, 222, 17, 27, 49, 113, 180, 91, 149, 185, 232, 2, 17, 0, 0, 0, 1, 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