Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f210f51d1c703c4f95339ea9599510be91eb02aee4d6b21adf5e793f02d0dc

Tx prefix hash: 68fe05794d6b37455abe32763c9452a19713fd7c1adf6302162c3ca650446a04
Tx public key: 622fda2752f9d5f1ef33dc00502158e3350a6c6788403f1f1be64da193fd3c95
Timestamp: 1697289953 Timestamp [UCT]: 2023-10-14 13:25:53 Age [y:d:h:m:s]: 01:187:04:57:56
Block: 869488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394832 RingCT/type: yes/0
Extra: 01622fda2752f9d5f1ef33dc00502158e3350a6c6788403f1f1be64da193fd3c95021100000011e6d27f9c000000000000000000

1 output(s) for total of 0.807282136000 dcy

stealth address amount amount idx
00: 099dfd0f54c0b8953bfa54781e7a5634e1ed701f344e5b2f532c961d59686f1b 0.807282136000 1324335 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": 869498, "vin": [ { "gen": { "height": 869488 } } ], "vout": [ { "amount": 807282136, "target": { "key": "099dfd0f54c0b8953bfa54781e7a5634e1ed701f344e5b2f532c961d59686f1b" } } ], "extra": [ 1, 98, 47, 218, 39, 82, 249, 213, 241, 239, 51, 220, 0, 80, 33, 88, 227, 53, 10, 108, 103, 136, 64, 63, 31, 27, 230, 77, 161, 147, 253, 60, 149, 2, 17, 0, 0, 0, 17, 230, 210, 127, 156, 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