Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010d84705a9c2de59e63b3e8ce3cafc6239ceaa9f71674affad6a6f557844505

Tx prefix hash: af93a385c54ba6fc76c86d4ce5e628a6d22c6892e82be54fe8eab7d8e946c98c
Tx public key: f10ca3cd9d3f415114614eae01cbefa810de24c86327f359b0633f33e35227fb
Timestamp: 1638252796 Timestamp [UCT]: 2021-11-30 06:13:16 Age [y:d:h:m:s]: 03:083:18:27:22
Block: 385179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 838531 RingCT/type: yes/0
Extra: 01f10ca3cd9d3f415114614eae01cbefa810de24c86327f359b0633f33e35227fb02110000000106faf294000000000000000000

1 output(s) for total of 32.490026831000 dcy

stealth address amount amount idx
00: 36ec04cce4d94a872d58eb521afb74594a955995d5fe5b9b37a6edb4d093bc17 32.490026831000 777322 of 0

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": 385189, "vin": [ { "gen": { "height": 385179 } } ], "vout": [ { "amount": 32490026831, "target": { "key": "36ec04cce4d94a872d58eb521afb74594a955995d5fe5b9b37a6edb4d093bc17" } } ], "extra": [ 1, 241, 12, 163, 205, 157, 63, 65, 81, 20, 97, 78, 174, 1, 203, 239, 168, 16, 222, 36, 200, 99, 39, 243, 89, 176, 99, 63, 51, 227, 82, 39, 251, 2, 17, 0, 0, 0, 1, 6, 250, 242, 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