Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 242abc50d4f9ae6d51a755607ecc0ccf1667d6a27dcc48bcf02819f2910af263

Tx prefix hash: 0ce8adb77ed887980fafa40af0e0e0068690d4da31f98ce874d660ab71156360
Tx public key: 0d2aaf754ab3bcd5c4f3f130d25266076f9f791bdc2bed398179bdb379f281d5
Timestamp: 1707675382 Timestamp [UCT]: 2024-02-11 18:16:22 Age [y:d:h:m:s]: 00:315:01:51:26
Block: 955372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225609 RingCT/type: yes/0
Extra: 010d2aaf754ab3bcd5c4f3f130d25266076f9f791bdc2bed398179bdb379f281d50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a49dc3c9f8c516668aad80f6e07b9a2329bc45804401bdd56c0d9f01c3eb513 0.600000000000 1414660 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": 955382, "vin": [ { "gen": { "height": 955372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a49dc3c9f8c516668aad80f6e07b9a2329bc45804401bdd56c0d9f01c3eb513" } } ], "extra": [ 1, 13, 42, 175, 117, 74, 179, 188, 213, 196, 243, 241, 48, 210, 82, 102, 7, 111, 159, 121, 27, 220, 43, 237, 57, 129, 121, 189, 179, 121, 242, 129, 213, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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