Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2f6458d0a5cc7a7fbf501d86a455826ebb2c9b16121ba2b8d555dc408a31215

Tx prefix hash: 85e65b1c4ebc97aa1a3f2b1d0b4d3d59d4a6f3c4a082e5bd88843b7b0043a9f0
Tx public key: a1434cd054bc6107c0e87aa424a307d68af5c9022498de25e46f5c29eae82f13
Timestamp: 1736307203 Timestamp [UCT]: 2025-01-08 03:33:23 Age [y:d:h:m:s]: 00:091:23:58:41
Block: 1192607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65544 RingCT/type: yes/0
Extra: 01a1434cd054bc6107c0e87aa424a307d68af5c9022498de25e46f5c29eae82f130211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f877b99376e32ac3d679e164bd076ea3fa4843e6d5e2653ae45e7c849eed431 0.600000000000 1679162 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": 1192617, "vin": [ { "gen": { "height": 1192607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f877b99376e32ac3d679e164bd076ea3fa4843e6d5e2653ae45e7c849eed431" } } ], "extra": [ 1, 161, 67, 76, 208, 84, 188, 97, 7, 192, 232, 122, 164, 36, 163, 7, 214, 138, 245, 201, 2, 36, 152, 222, 37, 228, 111, 92, 41, 234, 232, 47, 19, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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