Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dbf71b03c6517214866a729c6f872d752f9f6141c87f091dabef5248cee795f

Tx prefix hash: 58b71990583b6922a98e2b4658d17ec1da106a81e5a6efb8ca9185912ee1f958
Tx public key: 156407b103f36a79945e1c298d5b1576ea5fff605bee9e84162862a893ab7df4
Timestamp: 1744764915 Timestamp [UCT]: 2025-04-16 00:55:15 Age [y:d:h:m:s]: 00:048:02:04:21
Block: 1262360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34417 RingCT/type: yes/0
Extra: 01156407b103f36a79945e1c298d5b1576ea5fff605bee9e84162862a893ab7df40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2c5a8932a4fac81ccf9387c2e4233d3df3db538c9ffae1342c94fb61ac9308 0.600000000000 1749539 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": 1262370, "vin": [ { "gen": { "height": 1262360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2c5a8932a4fac81ccf9387c2e4233d3df3db538c9ffae1342c94fb61ac9308" } } ], "extra": [ 1, 21, 100, 7, 177, 3, 243, 106, 121, 148, 94, 28, 41, 141, 91, 21, 118, 234, 95, 255, 96, 91, 238, 158, 132, 22, 40, 98, 168, 147, 171, 125, 244, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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