Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16f8b3afc1be28a6aca5d71f3b9abd352818e656b399a9a7eb1e8d75eb3975a0

Tx prefix hash: 4d5bf65acfc09ed2d0fee572e35bb22bc014d001919f7e0b248e59a661cd150e
Tx public key: e53ae719aecacf70dc91137c8aa0cb2fac3e790d871f318948779a6586e59780
Timestamp: 1673774442 Timestamp [UCT]: 2023-01-15 09:20:42 Age [y:d:h:m:s]: 02:098:06:05:29
Block: 675178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591908 RingCT/type: yes/0
Extra: 01e53ae719aecacf70dc91137c8aa0cb2fac3e790d871f318948779a6586e59780021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.555125660000 dcy

stealth address amount amount idx
00: a81f8798a0b3b1c485f484ef6e441965f939d150999529381c697d1705bbb3c8 3.555125660000 1116849 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": 675188, "vin": [ { "gen": { "height": 675178 } } ], "vout": [ { "amount": 3555125660, "target": { "key": "a81f8798a0b3b1c485f484ef6e441965f939d150999529381c697d1705bbb3c8" } } ], "extra": [ 1, 229, 58, 231, 25, 174, 202, 207, 112, 220, 145, 19, 124, 138, 160, 203, 47, 172, 62, 121, 13, 135, 31, 49, 137, 72, 119, 154, 101, 134, 229, 151, 128, 2, 17, 0, 0, 0, 1, 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