Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc23498ad0584041131842b222201214661e5ce49ae813c1e6d2f741a397e62

Tx prefix hash: dc4b2a88eb3068e373a560cb5facd5bf7400f4845724ef352e5ccc2c7f1adbbb
Tx public key: 5c3c3406e8ddb84b5101138700a94f8d96162cfab8227a48ebd431421d2e2809
Timestamp: 1686007480 Timestamp [UCT]: 2023-06-05 23:24:40 Age [y:d:h:m:s]: 01:363:15:45:48
Block: 775980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521156 RingCT/type: yes/0
Extra: 015c3c3406e8ddb84b5101138700a94f8d96162cfab8227a48ebd431421d2e280902110000000133af99f4000000000000000000

1 output(s) for total of 1.647617137000 dcy

stealth address amount amount idx
00: d8aecb9c8d975f49aa71505f0d0bebfbfdcab45f9b0727619fc3983c4daeec13 1.647617137000 1225511 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": 775990, "vin": [ { "gen": { "height": 775980 } } ], "vout": [ { "amount": 1647617137, "target": { "key": "d8aecb9c8d975f49aa71505f0d0bebfbfdcab45f9b0727619fc3983c4daeec13" } } ], "extra": [ 1, 92, 60, 52, 6, 232, 221, 184, 75, 81, 1, 19, 135, 0, 169, 79, 141, 150, 22, 44, 250, 184, 34, 122, 72, 235, 212, 49, 66, 29, 46, 40, 9, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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