Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e2296cdf92ad0fa59bc3d9ab57e7da440c98874e7b3123907f0991e37a16bf

Tx prefix hash: 635632aef7fb221184036aaf6098312d5f2b3907c169ed0ff4289ea4080a93e9
Tx public key: 43f12620c716462ca4fb7d7db194f9668a4ed7fedf31bb33c4a56a3002659cd9
Timestamp: 1704557286 Timestamp [UCT]: 2024-01-06 16:08:06 Age [y:d:h:m:s]: 01:156:13:20:11
Block: 929511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373033 RingCT/type: yes/0
Extra: 0143f12620c716462ca4fb7d7db194f9668a4ed7fedf31bb33c4a56a3002659cd90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf2b3a1694645d8346e5cf465c3db2072f5bc1697a227d145d1a7df83510a9b5 0.600000000000 1387387 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": 929521, "vin": [ { "gen": { "height": 929511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf2b3a1694645d8346e5cf465c3db2072f5bc1697a227d145d1a7df83510a9b5" } } ], "extra": [ 1, 67, 241, 38, 32, 199, 22, 70, 44, 164, 251, 125, 125, 177, 148, 249, 102, 138, 78, 215, 254, 223, 49, 187, 51, 196, 165, 106, 48, 2, 101, 156, 217, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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