Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c3a30862825b81a7ce6afdbe2867123ea01edf431930faa8005e732047f61eb

Tx prefix hash: 116bdd71e552c97d7de6b3c447fe3c5d633cfd98db5550a5a008de99a05c61d8
Tx public key: a77e81a9d7be3a21182ba57fd12325a80006a3d89de9edf823d6be4c2d2e4082
Timestamp: 1712369536 Timestamp [UCT]: 2024-04-06 02:12:16 Age [y:d:h:m:s]: 01:010:11:04:35
Block: 994262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268466 RingCT/type: yes/0
Extra: 01a77e81a9d7be3a21182ba57fd12325a80006a3d89de9edf823d6be4c2d2e408202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3febe003de8c9e72e2536e8a80387a7500a1641cd26d34ff6878b5abe5de0515 0.600000000000 1454664 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": 994272, "vin": [ { "gen": { "height": 994262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3febe003de8c9e72e2536e8a80387a7500a1641cd26d34ff6878b5abe5de0515" } } ], "extra": [ 1, 167, 126, 129, 169, 215, 190, 58, 33, 24, 43, 165, 127, 209, 35, 37, 168, 0, 6, 163, 216, 157, 233, 237, 248, 35, 214, 190, 76, 45, 46, 64, 130, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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