Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f21681912cfc412f2a58cc284a37124f55d57e1f6da479395d5d17286c07a46a

Tx prefix hash: 3534b6263cfe3f89ca2cbe6535dca20c6cb719fe8b2e0630f55082bd3193ee0e
Tx public key: 9a8ab1e8112cf5e3e4c3d74d0702f3f9ea52ff0e713ea0a081e27d5545ee9321
Timestamp: 1721071380 Timestamp [UCT]: 2024-07-15 19:23:00 Age [y:d:h:m:s]: 00:253:11:18:10
Block: 1066456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181048 RingCT/type: yes/0
Extra: 019a8ab1e8112cf5e3e4c3d74d0702f3f9ea52ff0e713ea0a081e27d5545ee9321021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdee2b9a31ae39f756b9e0d1851940821bfc270f5619af3a56816b2301256a8d 0.600000000000 1537059 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": 1066466, "vin": [ { "gen": { "height": 1066456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdee2b9a31ae39f756b9e0d1851940821bfc270f5619af3a56816b2301256a8d" } } ], "extra": [ 1, 154, 138, 177, 232, 17, 44, 245, 227, 228, 195, 215, 77, 7, 2, 243, 249, 234, 82, 255, 14, 113, 62, 160, 160, 129, 226, 125, 85, 69, 238, 147, 33, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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