Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: add49c7650f2eaa4dcad197705aa10f7e022bd3dc5bf0d3877782290abd5b0be

Tx prefix hash: 03d21c5c3d8e6307d8bd84f6b319d270ec53f3ce1daff0d54a91bc9c2dd5fd5c
Tx public key: 07c3a9f8e1aa094971354366cc828ed683fe3daf07aa1db4da0532dc54cd7e2b
Timestamp: 1578090193 Timestamp [UCT]: 2020-01-03 22:23:13 Age [y:d:h:m:s]: 05:030:19:30:40
Block: 38036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171907 RingCT/type: yes/0
Extra: 0107c3a9f8e1aa094971354366cc828ed683fe3daf07aa1db4da0532dc54cd7e2b02110000006231ef32d6000000000000000000

1 output(s) for total of 459.168189363000 dcy

stealth address amount amount idx
00: 1771a48ffcb1222d29467e2ac43f705a3085e3ec62d281302ecd1b0a6a6fd5f7 459.168189363000 64683 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": 38046, "vin": [ { "gen": { "height": 38036 } } ], "vout": [ { "amount": 459168189363, "target": { "key": "1771a48ffcb1222d29467e2ac43f705a3085e3ec62d281302ecd1b0a6a6fd5f7" } } ], "extra": [ 1, 7, 195, 169, 248, 225, 170, 9, 73, 113, 53, 67, 102, 204, 130, 142, 214, 131, 254, 61, 175, 7, 170, 29, 180, 218, 5, 50, 220, 84, 205, 126, 43, 2, 17, 0, 0, 0, 98, 49, 239, 50, 214, 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