Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2e4ee3157ee081d7b1742cf0573913b6843503b5fb32007d1479886b7ef6e8

Tx prefix hash: 6aafeda7b9bd4a71c9ac3f162d3e753a6182344593e3182a557403bae4c2146b
Tx public key: 0a188aaa7ca38a0ef8bec55b0c4d274f7b0a2f1bf2a10d182f6afe455f611018
Timestamp: 1578344951 Timestamp [UCT]: 2020-01-06 21:09:11 Age [y:d:h:m:s]: 04:361:11:26:41
Block: 40037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147718 RingCT/type: yes/0
Extra: 010a188aaa7ca38a0ef8bec55b0c4d274f7b0a2f1bf2a10d182f6afe455f61101802110000002b2264afe6000000000000000000

1 output(s) for total of 452.211545732000 dcy

stealth address amount amount idx
00: e2542c670052b1ac6cd00c25c7099e7187d2d13d21cfd90a0b9c43920b17efd2 452.211545732000 69817 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": 40047, "vin": [ { "gen": { "height": 40037 } } ], "vout": [ { "amount": 452211545732, "target": { "key": "e2542c670052b1ac6cd00c25c7099e7187d2d13d21cfd90a0b9c43920b17efd2" } } ], "extra": [ 1, 10, 24, 138, 170, 124, 163, 138, 14, 248, 190, 197, 91, 12, 77, 39, 79, 123, 10, 47, 27, 242, 161, 13, 24, 47, 106, 254, 69, 95, 97, 16, 24, 2, 17, 0, 0, 0, 43, 34, 100, 175, 230, 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