Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09edc758a8ac253afc051fc7a42a3857c62a0e13857742c4b88674a369ee847a

Tx prefix hash: 8348b3937b65f3b60130984d117b9a0c913f7f3fe08a722e2009a325c1638945
Tx public key: a02818cd910303a909424fd633c9b41076bc8a08078fb44f2ca2b04562f6c605
Timestamp: 1703511800 Timestamp [UCT]: 2023-12-25 13:43:20 Age [y:d:h:m:s]: 01:320:19:30:22
Block: 920862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488118 RingCT/type: yes/0
Extra: 01a02818cd910303a909424fd633c9b41076bc8a08078fb44f2ca2b04562f6c605021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 245dcccd896f6f4d4acbba18eb68d0b0eab34eb5b2cb86434bafbde0dbd72950 0.600000000000 1378546 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": 920872, "vin": [ { "gen": { "height": 920862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "245dcccd896f6f4d4acbba18eb68d0b0eab34eb5b2cb86434bafbde0dbd72950" } } ], "extra": [ 1, 160, 40, 24, 205, 145, 3, 3, 169, 9, 66, 79, 214, 51, 201, 180, 16, 118, 188, 138, 8, 7, 143, 180, 79, 44, 162, 176, 69, 98, 246, 198, 5, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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