Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379207c1e8fc10fc73c28d2944645e8ec781d29a5abef55d1518174bb2cf34f6

Tx prefix hash: c4028be6ada9cbcca8b5b8bf4b0cd89f2658798b86e29c503a320ff42a0b7b63
Tx public key: ba6b5aaf2caa138a353a47e58d5fd4c1b84cb437664edee1b47c4f1d6ae6dd52
Timestamp: 1677953413 Timestamp [UCT]: 2023-03-04 18:10:13 Age [y:d:h:m:s]: 02:029:14:42:50
Block: 709858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542720 RingCT/type: yes/0
Extra: 01ba6b5aaf2caa138a353a47e58d5fd4c1b84cb437664edee1b47c4f1d6ae6dd520211000000015029cbac000000000000000000

1 output(s) for total of 2.728636403000 dcy

stealth address amount amount idx
00: 1a4f99e9a5586a04b4d304df664ceb485b2a9ae6ec40ac5b4e8d42ed44cde763 2.728636403000 1153877 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": 709868, "vin": [ { "gen": { "height": 709858 } } ], "vout": [ { "amount": 2728636403, "target": { "key": "1a4f99e9a5586a04b4d304df664ceb485b2a9ae6ec40ac5b4e8d42ed44cde763" } } ], "extra": [ 1, 186, 107, 90, 175, 44, 170, 19, 138, 53, 58, 71, 229, 141, 95, 212, 193, 184, 76, 180, 55, 102, 78, 222, 225, 180, 124, 79, 29, 106, 230, 221, 82, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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