Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169b833526efdba58deff419a4175484e0d876e303ae2aaf927df929a756ea7a

Tx prefix hash: 8e7b905ee439d76d3b4e57483cd4a5e8221c387e5ffce004db072f2f8a35263d
Tx public key: 0a12874dd4cac1e4a0d7a50b2d0073b7c838105328fdaee5fdc4f716e0d31294
Timestamp: 1702432684 Timestamp [UCT]: 2023-12-13 01:58:04 Age [y:d:h:m:s]: 01:117:13:24:31
Block: 911928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345146 RingCT/type: yes/0
Extra: 010a12874dd4cac1e4a0d7a50b2d0073b7c838105328fdaee5fdc4f716e0d31294021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdc0b95accb2ea1386f54fae703c984ad9ef6c88940b5f532f73820c9e716019 0.600000000000 1369144 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": 911938, "vin": [ { "gen": { "height": 911928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdc0b95accb2ea1386f54fae703c984ad9ef6c88940b5f532f73820c9e716019" } } ], "extra": [ 1, 10, 18, 135, 77, 212, 202, 193, 228, 160, 215, 165, 11, 45, 0, 115, 183, 200, 56, 16, 83, 40, 253, 174, 229, 253, 196, 247, 22, 224, 211, 18, 148, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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