Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5335aa0e518b57c5baef94ae0eef40c9d4de39d661b27925caf9b64325f55443

Tx prefix hash: 7df1bf64a47390863f9593b46843899645d178d5560063963b54147cf0da27fe
Tx public key: ebbd1194de8421fa2d1a876c99526bea4b4eb47395e2d591c891f1fb90a6680e
Timestamp: 1716433510 Timestamp [UCT]: 2024-05-23 03:05:10 Age [y:d:h:m:s]: 00:315:05:46:36
Block: 1027990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225306 RingCT/type: yes/0
Extra: 01ebbd1194de8421fa2d1a876c99526bea4b4eb47395e2d591c891f1fb90a6680e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df17525e6db1c5a8d1df6ec2ebdf6840dcfbb6708b4da58d1660eccbee557056 0.600000000000 1495881 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": 1028000, "vin": [ { "gen": { "height": 1027990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df17525e6db1c5a8d1df6ec2ebdf6840dcfbb6708b4da58d1660eccbee557056" } } ], "extra": [ 1, 235, 189, 17, 148, 222, 132, 33, 250, 45, 26, 135, 108, 153, 82, 107, 234, 75, 78, 180, 115, 149, 226, 213, 145, 200, 145, 241, 251, 144, 166, 104, 14, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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