Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b70c16f67622d64ca5dfa994ab8b8010cf64335b1c4c16527f1558ade2f4ef

Tx prefix hash: 2f067c4127e7250be87d494bd74cca7190869b9adbaedeeb5b0b5d24c317b878
Tx public key: 6177ddb4bce6a39326b60634cccb799341c82e703e625f64980a4d5aae4298d5
Timestamp: 1727659414 Timestamp [UCT]: 2024-09-30 01:23:34 Age [y:d:h:m:s]: 01:038:20:00:45
Block: 1121056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286145 RingCT/type: yes/0
Extra: 016177ddb4bce6a39326b60634cccb799341c82e703e625f64980a4d5aae4298d502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38c391bb14c7214d2c504bd862cf261e8d177715c4659a120ab0c2bbd328f10d 0.600000000000 1603191 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": 1121066, "vin": [ { "gen": { "height": 1121056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38c391bb14c7214d2c504bd862cf261e8d177715c4659a120ab0c2bbd328f10d" } } ], "extra": [ 1, 97, 119, 221, 180, 188, 230, 163, 147, 38, 182, 6, 52, 204, 203, 121, 147, 65, 200, 46, 112, 62, 98, 95, 100, 152, 10, 77, 90, 174, 66, 152, 213, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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