Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e290ebcad5b8ed8058380106a4cd9cae84f4287f437cbeba826637c2d5a28686

Tx prefix hash: 2dfa5409d95acc02fd94d2cf9374b42369278bbc172ee5670f5d268c70c65ae3
Tx public key: 9f21cf89a855d5ec663163fe985fbc8d6cd018c0e8f88079b8373b9601e6e212
Timestamp: 1693992857 Timestamp [UCT]: 2023-09-06 09:34:17 Age [y:d:h:m:s]: 01:212:02:46:08
Block: 842122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412722 RingCT/type: yes/0
Extra: 019f21cf89a855d5ec663163fe985fbc8d6cd018c0e8f88079b8373b9601e6e21202110000000d4b8f5122000000000000000000

1 output(s) for total of 0.994718742000 dcy

stealth address amount amount idx
00: 1f0f5baa44d13fe9f43ebfa4be265e5ae00021eef726932f6ea00c5695850ac6 0.994718742000 1295214 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": 842132, "vin": [ { "gen": { "height": 842122 } } ], "vout": [ { "amount": 994718742, "target": { "key": "1f0f5baa44d13fe9f43ebfa4be265e5ae00021eef726932f6ea00c5695850ac6" } } ], "extra": [ 1, 159, 33, 207, 137, 168, 85, 213, 236, 102, 49, 99, 254, 152, 95, 188, 141, 108, 208, 24, 192, 232, 248, 128, 121, 184, 55, 59, 150, 1, 230, 226, 18, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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