Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624d70a2ae159b1bdb3c894a9ae17cfea7ad2fa60469d13da14a2f7e5d408cc3

Tx prefix hash: df88e5adc8a69518910cad202c626283958aba32ddcd0e1a31967f6cd7cb124b
Tx public key: 76013dbb42a6ebb05d2bf5e9cb30c5638bc6afbe21cb92dc4e0dcaf38e007350
Timestamp: 1690022837 Timestamp [UCT]: 2023-07-22 10:47:17 Age [y:d:h:m:s]: 01:220:06:02:02
Block: 809294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418489 RingCT/type: yes/0
Extra: 0176013dbb42a6ebb05d2bf5e9cb30c5638bc6afbe21cb92dc4e0dcaf38e00735002110000000175e3f0e9000000000000000000

1 output(s) for total of 1.277830178000 dcy

stealth address amount amount idx
00: 9837c5b769fd30c41106907af913704a62437548f41bdbd58892c4385410568c 1.277830178000 1260897 of 0

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": 809304, "vin": [ { "gen": { "height": 809294 } } ], "vout": [ { "amount": 1277830178, "target": { "key": "9837c5b769fd30c41106907af913704a62437548f41bdbd58892c4385410568c" } } ], "extra": [ 1, 118, 1, 61, 187, 66, 166, 235, 176, 93, 43, 245, 233, 203, 48, 197, 99, 139, 198, 175, 190, 33, 203, 146, 220, 78, 13, 202, 243, 142, 0, 115, 80, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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