Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f47d5dfb12d0172e7d997312bf09ca75ee92bd15b2e906bada128f92b0d87480

Tx prefix hash: 53a09111149a1a45c14d5fcc9cbd2e9d338bcaf56a5ff6f4172cba8fd75a9c84
Tx public key: 1ee133d1b724e1bcac412f883a65e462289fb603e6af82ca276cdbfddd32ca2e
Timestamp: 1716814131 Timestamp [UCT]: 2024-05-27 12:48:51 Age [y:d:h:m:s]: 00:308:04:24:44
Block: 1031157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220243 RingCT/type: yes/0
Extra: 011ee133d1b724e1bcac412f883a65e462289fb603e6af82ca276cdbfddd32ca2e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ade691b45acc61f4e75992424c2671922b2dcb311cd05efed3f92b46724c6e4 0.600000000000 1499532 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": 1031167, "vin": [ { "gen": { "height": 1031157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ade691b45acc61f4e75992424c2671922b2dcb311cd05efed3f92b46724c6e4" } } ], "extra": [ 1, 30, 225, 51, 209, 183, 36, 225, 188, 172, 65, 47, 136, 58, 101, 228, 98, 40, 159, 182, 3, 230, 175, 130, 202, 39, 108, 219, 253, 221, 50, 202, 46, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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