Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449de030d0a88089cfd9928664e6520bf6b5919dca0c8fe9aa6854e527edb9e8

Tx prefix hash: 6b2f5f06e42413f813fd1423bc1350108866659b6cfbad364410c0a053f4463f
Tx public key: 9be3bd3f0aa716a7e991b33a82fc02f53c56be23182d5a3431d566873147e2ce
Timestamp: 1717500584 Timestamp [UCT]: 2024-06-04 11:29:44 Age [y:d:h:m:s]: 00:292:15:15:58
Block: 1036849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209108 RingCT/type: yes/0
Extra: 019be3bd3f0aa716a7e991b33a82fc02f53c56be23182d5a3431d566873147e2ce0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 882546844489b2c4169ab6116f0d136fca5c4177e580ce9dd20154d16a0ef56d 0.600000000000 1505378 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": 1036859, "vin": [ { "gen": { "height": 1036849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "882546844489b2c4169ab6116f0d136fca5c4177e580ce9dd20154d16a0ef56d" } } ], "extra": [ 1, 155, 227, 189, 63, 10, 167, 22, 167, 233, 145, 179, 58, 130, 252, 2, 245, 60, 86, 190, 35, 24, 45, 90, 52, 49, 213, 102, 135, 49, 71, 226, 206, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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