Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf3a7d86f29c8c3dbe89c042389502c4889e084657b654bcc53058fd0230862

Tx prefix hash: a0830bc440c0a76609f6ce5c2fd17789bf0854b4d6bae22ad37b526a59d4f481
Tx public key: 8c0d2a4a05f001ec96cd5f0c496022dcff9547511ddefeca8cadff15eba333e4
Timestamp: 1711423348 Timestamp [UCT]: 2024-03-26 03:22:28 Age [y:d:h:m:s]: 01:270:12:26:08
Block: 986478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452062 RingCT/type: yes/0
Extra: 018c0d2a4a05f001ec96cd5f0c496022dcff9547511ddefeca8cadff15eba333e402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c98fdef2ea9bb300008495b03ffd2e72f34b429d143bb97fd0d88df38a6167ee 0.600000000000 1446707 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": 986488, "vin": [ { "gen": { "height": 986478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c98fdef2ea9bb300008495b03ffd2e72f34b429d143bb97fd0d88df38a6167ee" } } ], "extra": [ 1, 140, 13, 42, 74, 5, 240, 1, 236, 150, 205, 95, 12, 73, 96, 34, 220, 255, 149, 71, 81, 29, 222, 254, 202, 140, 173, 255, 21, 235, 163, 51, 228, 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