Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f836c4c60a20724e67bc24c8416909564e04a55492d75052d172cd8c83477782

Tx prefix hash: 7eaf625338d5cb72d04a4fb51140710bfd353bbee5ab62bb7fe849c6f73d3d0b
Tx public key: 8c1c5fb9be3d8ed9e6c8ab5fb48f07ad5bb42d83a6475055aaa85e213166ace9
Timestamp: 1711345599 Timestamp [UCT]: 2024-03-25 05:46:39 Age [y:d:h:m:s]: 01:009:19:56:20
Block: 985827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267967 RingCT/type: yes/0
Extra: 018c1c5fb9be3d8ed9e6c8ab5fb48f07ad5bb42d83a6475055aaa85e213166ace90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c18ef7bb3ccfcf1c7207e6f078da232a4395ed8d2932bbbfbe65aa68eb6085e5 0.600000000000 1446048 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": 985837, "vin": [ { "gen": { "height": 985827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c18ef7bb3ccfcf1c7207e6f078da232a4395ed8d2932bbbfbe65aa68eb6085e5" } } ], "extra": [ 1, 140, 28, 95, 185, 190, 61, 142, 217, 230, 200, 171, 95, 180, 143, 7, 173, 91, 180, 45, 131, 166, 71, 80, 85, 170, 168, 94, 33, 49, 102, 172, 233, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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