Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df93ab83a3ce51ae9d8d95ad71627f24c80f7babc063ab395a19fb810dc031e5

Tx prefix hash: 07856200d64b0b9da345b34bc87545837c17fa346c225a07933b3646c7b09714
Tx public key: 7989af9bbc6d1787856e62d3218d0d92be640fdbe3206cf271914c6cd11e3a7a
Timestamp: 1583856865 Timestamp [UCT]: 2020-03-10 16:14:25 Age [y:d:h:m:s]: 04:359:08:27:36
Block: 79947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151649 RingCT/type: yes/0
Extra: 017989af9bbc6d1787856e62d3218d0d92be640fdbe3206cf271914c6cd11e3a7a021100000005203e3db0000000000000000000

1 output(s) for total of 333.505646654000 dcy

stealth address amount amount idx
00: 79729072f55a789279c73f9cde7ffaae8fe68e6a5bec54c52995b74eb4cf05de 333.505646654000 146279 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": 79957, "vin": [ { "gen": { "height": 79947 } } ], "vout": [ { "amount": 333505646654, "target": { "key": "79729072f55a789279c73f9cde7ffaae8fe68e6a5bec54c52995b74eb4cf05de" } } ], "extra": [ 1, 121, 137, 175, 155, 188, 109, 23, 135, 133, 110, 98, 211, 33, 141, 13, 146, 190, 100, 15, 219, 227, 32, 108, 242, 113, 145, 76, 108, 209, 30, 58, 122, 2, 17, 0, 0, 0, 5, 32, 62, 61, 176, 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