Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d020b967c2a99c77f3cf6db118c84759faf28359093ee82ac8a7a47f36d8a078

Tx prefix hash: f9d2b022c3845e94786f0d8d4c303114f91c61915000cff8b9f633b5d60b45db
Tx public key: e543b84133f82d97a9f6be8e1413f5b7a6b6858e891663d60e114d4016f2171e
Timestamp: 1649710968 Timestamp [UCT]: 2022-04-11 21:02:48 Age [y:d:h:m:s]: 02:259:00:36:21
Block: 478158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704987 RingCT/type: yes/0
Extra: 01e543b84133f82d97a9f6be8e1413f5b7a6b6858e891663d60e114d4016f2171e02110000001aa8c141c5000000000000000000

1 output(s) for total of 15.983220492000 dcy

stealth address amount amount idx
00: 0debb700fcee49013f9aa48e619385ef46029e22a9bdc65fdc988a4d6fd1ca79 15.983220492000 898889 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": 478168, "vin": [ { "gen": { "height": 478158 } } ], "vout": [ { "amount": 15983220492, "target": { "key": "0debb700fcee49013f9aa48e619385ef46029e22a9bdc65fdc988a4d6fd1ca79" } } ], "extra": [ 1, 229, 67, 184, 65, 51, 248, 45, 151, 169, 246, 190, 142, 20, 19, 245, 183, 166, 182, 133, 142, 137, 22, 99, 214, 14, 17, 77, 64, 22, 242, 23, 30, 2, 17, 0, 0, 0, 26, 168, 193, 65, 197, 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