Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87178bfddd0f89ab08d0ca56675be93a0342930f484f77bd4138ab9ceaad1fe

Tx prefix hash: dc5af68295bf393ad731a70cb7b44ee2738a3ff79f56973b05ee0a46233dddf7
Tx public key: 5fe9b15ecffec1503be26c1e88768fb5c1b52bfb4b43c456a1cc177c08af57dc
Timestamp: 1727012407 Timestamp [UCT]: 2024-09-22 13:40:07 Age [y:d:h:m:s]: 00:063:04:02:51
Block: 1115694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45147 RingCT/type: yes/0
Extra: 015fe9b15ecffec1503be26c1e88768fb5c1b52bfb4b43c456a1cc177c08af57dc02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db4b0c4c7a6c3f3ef7e79c2ea7a6cb9a446c133a945213e93d18c89bba87de8c 0.600000000000 1595915 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": 1115704, "vin": [ { "gen": { "height": 1115694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db4b0c4c7a6c3f3ef7e79c2ea7a6cb9a446c133a945213e93d18c89bba87de8c" } } ], "extra": [ 1, 95, 233, 177, 94, 207, 254, 193, 80, 59, 226, 108, 30, 136, 118, 143, 181, 193, 181, 43, 251, 75, 67, 196, 86, 161, 204, 23, 124, 8, 175, 87, 220, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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