Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9131a56294c3e4e34fdb8111c1e40349713b68ff202541bef57561389a66f43

Tx prefix hash: f72da37b494cdab38ff3ab39bb2cddc56b0c8b517e9a700dd44bfd8ceb7cd1aa
Tx public key: 67373fe2acfbf9f3e7b70753825a95d6a8057fc260b8ccea83d62c753a7c79cc
Timestamp: 1704956970 Timestamp [UCT]: 2024-01-11 07:09:30 Age [y:d:h:m:s]: 01:045:12:58:01
Block: 932823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293622 RingCT/type: yes/0
Extra: 0167373fe2acfbf9f3e7b70753825a95d6a8057fc260b8ccea83d62c753a7c79cc0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8799afb6a3629224825a5a841efb8e5d10f3a5ee0914853a16b0f98625f8a469 0.600000000000 1390763 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": 932833, "vin": [ { "gen": { "height": 932823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8799afb6a3629224825a5a841efb8e5d10f3a5ee0914853a16b0f98625f8a469" } } ], "extra": [ 1, 103, 55, 63, 226, 172, 251, 249, 243, 231, 183, 7, 83, 130, 90, 149, 214, 168, 5, 127, 194, 96, 184, 204, 234, 131, 214, 44, 117, 58, 124, 121, 204, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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