Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e7d1c18c63d350b902faf5759974535e377ecd0637c900de4c885f0f8c23d20

Tx prefix hash: 60fc7ed40bd2c3924a663d38f91a0b93ecfc11af972e50585f017c9313a8cc36
Tx public key: 4816340db1d89c6be5ce3d46fd11bf97cfbae3df4cfe01ddfe05bd7dd68e72f0
Timestamp: 1736577506 Timestamp [UCT]: 2025-01-11 06:38:26 Age [y:d:h:m:s]: 00:082:16:43:39
Block: 1194858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58871 RingCT/type: yes/0
Extra: 014816340db1d89c6be5ce3d46fd11bf97cfbae3df4cfe01ddfe05bd7dd68e72f0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c001c0cea9c58b35363b205e3fb75c47590ba0f4f05fee59667cc46064a9fb8 0.600000000000 1681435 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": 1194868, "vin": [ { "gen": { "height": 1194858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c001c0cea9c58b35363b205e3fb75c47590ba0f4f05fee59667cc46064a9fb8" } } ], "extra": [ 1, 72, 22, 52, 13, 177, 216, 156, 107, 229, 206, 61, 70, 253, 17, 191, 151, 207, 186, 227, 223, 76, 254, 1, 221, 254, 5, 189, 125, 214, 142, 114, 240, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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