Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfed451e85776ae099ac91b37cc1e989a90ca4a60335f2eea3980a42df907b3

Tx prefix hash: 5f96f96a14f5e6b0830be30f1b7d9a4afb66f4a96e331e8a8982704fd8c20410
Tx public key: 684977dc382bfefed51943090bd67de43b137eb9edc6b0eeca0d2c01a409d831
Timestamp: 1709965093 Timestamp [UCT]: 2024-03-09 06:18:13 Age [y:d:h:m:s]: 01:251:20:09:57
Block: 974371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438708 RingCT/type: yes/0
Extra: 01684977dc382bfefed51943090bd67de43b137eb9edc6b0eeca0d2c01a409d83102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0477f5c10d2140d818c626a7b0dbcf4c2978a298948835302a627e0a74e21b0 0.600000000000 1434326 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": 974381, "vin": [ { "gen": { "height": 974371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0477f5c10d2140d818c626a7b0dbcf4c2978a298948835302a627e0a74e21b0" } } ], "extra": [ 1, 104, 73, 119, 220, 56, 43, 254, 254, 213, 25, 67, 9, 11, 214, 125, 228, 59, 19, 126, 185, 237, 198, 176, 238, 202, 13, 44, 1, 164, 9, 216, 49, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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