Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14078bbc3c8cf517216f8a9adbee68455a4b0b3027dba47f5e4689b9bf219505

Tx prefix hash: 31c157034133bdde3715099da7f30db5b2cdbfe484c3b9881c215c25c487fe2a
Tx public key: e80b8e4093a75d3cb5860ea996e4978b439b3701ce9b82f9b8dfd2d4291338e4
Timestamp: 1736932440 Timestamp [UCT]: 2025-01-15 09:14:00 Age [y:d:h:m:s]: 00:153:22:07:28
Block: 1197783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109714 RingCT/type: yes/0
Extra: 01e80b8e4093a75d3cb5860ea996e4978b439b3701ce9b82f9b8dfd2d4291338e40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2926440206742df8bc62e93fb4ec0a3e62c56e4a380a30a644f79ddcc08bffdc 0.600000000000 1684400 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": 1197793, "vin": [ { "gen": { "height": 1197783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2926440206742df8bc62e93fb4ec0a3e62c56e4a380a30a644f79ddcc08bffdc" } } ], "extra": [ 1, 232, 11, 142, 64, 147, 167, 93, 60, 181, 134, 14, 169, 150, 228, 151, 139, 67, 155, 55, 1, 206, 155, 130, 249, 184, 223, 210, 212, 41, 19, 56, 228, 2, 17, 0, 0, 0, 3, 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