Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 861a6373df13fe4b8f9aac597ebbc10560cd73c0529b9edbab871ca6d71e0677

Tx prefix hash: 135c10190deec122cd5eeb9326e0a402181cc76d0851b2a2d59eb4f215646af1
Tx public key: 998179be98beeac73fb8c38a1e085d3fb324aa8ffb9490fad2172ca514e26475
Timestamp: 1735188185 Timestamp [UCT]: 2024-12-26 04:43:05 Age [y:d:h:m:s]: 00:322:23:19:35
Block: 1183361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228334 RingCT/type: yes/0
Extra: 01998179be98beeac73fb8c38a1e085d3fb324aa8ffb9490fad2172ca514e26475021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6cb200d6cc8dfd4e66b63f754640028eab20b3ff4f4c885dce0a2adcfc14fa 0.600000000000 1669806 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": 1183371, "vin": [ { "gen": { "height": 1183361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6cb200d6cc8dfd4e66b63f754640028eab20b3ff4f4c885dce0a2adcfc14fa" } } ], "extra": [ 1, 153, 129, 121, 190, 152, 190, 234, 199, 63, 184, 195, 138, 30, 8, 93, 63, 179, 36, 170, 143, 251, 148, 144, 250, 210, 23, 44, 165, 20, 226, 100, 117, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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