Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6a296d606039c05d1b85bb7e1c5314931dab039d7bcf71ca160d75f405f76d

Tx prefix hash: 30dde97557c73592e2c2f9ad4580179b28d44a74f5cea0544d7f671dbbd4bbd1
Tx public key: f63d3e155e422706d8b968196f38e5fe5676c17bc96a31c191f5bdd13a418a05
Timestamp: 1720825746 Timestamp [UCT]: 2024-07-12 23:09:06 Age [y:d:h:m:s]: 00:224:21:59:36
Block: 1064416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160627 RingCT/type: yes/0
Extra: 01f63d3e155e422706d8b968196f38e5fe5676c17bc96a31c191f5bdd13a418a05021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472919790cedfcaa64efa426bb50f5aa111f9ab610c885685b5d89c5858d81ea 0.600000000000 1534941 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": 1064426, "vin": [ { "gen": { "height": 1064416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472919790cedfcaa64efa426bb50f5aa111f9ab610c885685b5d89c5858d81ea" } } ], "extra": [ 1, 246, 61, 62, 21, 94, 66, 39, 6, 216, 185, 104, 25, 111, 56, 229, 254, 86, 118, 193, 123, 201, 106, 49, 193, 145, 245, 189, 209, 58, 65, 138, 5, 2, 17, 0, 0, 0, 1, 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