Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f2213d9389bb6f4758b701321385e0fd8fb62e03018bbc9e317b1b54dd86fe6

Tx prefix hash: 99b82d05d92a4cbd25989a6ca0480fb77bf92cc09a6a9d1f1dd65437c12ae890
Tx public key: b7f8e780ac676d0f32fbd6567b4513ca1168092b1ef805572e3da94da0f4363c
Timestamp: 1696236872 Timestamp [UCT]: 2023-10-02 08:54:32 Age [y:d:h:m:s]: 01:257:02:14:24
Block: 860750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444737 RingCT/type: yes/0
Extra: 01b7f8e780ac676d0f32fbd6567b4513ca1168092b1ef805572e3da94da0f4363c02110000000be6d27f9c000000000000000000

1 output(s) for total of 0.862934786000 dcy

stealth address amount amount idx
00: 3c49f26ded71054b2383b41fcb39eec4dc968a116113eedcacb9cb5d6745b8f6 0.862934786000 1315048 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": 860760, "vin": [ { "gen": { "height": 860750 } } ], "vout": [ { "amount": 862934786, "target": { "key": "3c49f26ded71054b2383b41fcb39eec4dc968a116113eedcacb9cb5d6745b8f6" } } ], "extra": [ 1, 183, 248, 231, 128, 172, 103, 109, 15, 50, 251, 214, 86, 123, 69, 19, 202, 17, 104, 9, 43, 30, 248, 5, 87, 46, 61, 169, 77, 160, 244, 54, 60, 2, 17, 0, 0, 0, 11, 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