Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a477d622d79ee1113c61934648859ff314de3bb0c518ed8d4497242cd9e62115

Tx prefix hash: 21d6e0a9864bf73962e3a2166a9a6b6ae38d40c2f0dea7c413526faf0317dfc3
Tx public key: 24cc36a7f694dc8bfc9f0d7c7a04173403093f36f54bd84bd2a5175cead93fe4
Timestamp: 1703041148 Timestamp [UCT]: 2023-12-20 02:59:08 Age [y:d:h:m:s]: 01:116:01:24:29
Block: 916955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344097 RingCT/type: yes/0
Extra: 0124cc36a7f694dc8bfc9f0d7c7a04173403093f36f54bd84bd2a5175cead93fe4021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de1f1f75e6620dedaa701c49ae7a0fcf7ca1459401f68fc3e86e2dd022268455 0.600000000000 1374517 of 15

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": 916965, "vin": [ { "gen": { "height": 916955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de1f1f75e6620dedaa701c49ae7a0fcf7ca1459401f68fc3e86e2dd022268455" } } ], "extra": [ 1, 36, 204, 54, 167, 246, 148, 220, 139, 252, 159, 13, 124, 122, 4, 23, 52, 3, 9, 63, 54, 245, 75, 216, 75, 210, 165, 23, 92, 234, 217, 63, 228, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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