Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df44874b3d406c892b2d7568f9bb157d75aaaf8f6444d82e40d2aa71db3efdd0

Tx prefix hash: fb956358cd501b4791dc3eb307d5692bc137e801f415cff01061812b577f1bbd
Tx public key: 4d1da01d7ed8229c2b47349aeb57e3c255e99ef83bded43c5f4dcd5afbda709d
Timestamp: 1715274584 Timestamp [UCT]: 2024-05-09 17:09:44 Age [y:d:h:m:s]: 00:316:22:40:53
Block: 1018385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226552 RingCT/type: yes/0
Extra: 014d1da01d7ed8229c2b47349aeb57e3c255e99ef83bded43c5f4dcd5afbda709d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03ebbfced24087da634f6cb1dee0c0e508d4de8664f9595da172ba2d2df4a373 0.600000000000 1482174 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": 1018395, "vin": [ { "gen": { "height": 1018385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03ebbfced24087da634f6cb1dee0c0e508d4de8664f9595da172ba2d2df4a373" } } ], "extra": [ 1, 77, 29, 160, 29, 126, 216, 34, 156, 43, 71, 52, 154, 235, 87, 227, 194, 85, 233, 158, 248, 59, 222, 212, 60, 95, 77, 205, 90, 251, 218, 112, 157, 2, 17, 0, 0, 0, 1, 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