Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf19f7cfc34afbb24a1c41d624cfdc08adbfa958ddb835be5136367ef587ef6

Tx prefix hash: b724908d64fcba1b9034dcb561d62d53883dc1640b03a5f5269dafb66b0566a0
Tx public key: c49fcb1c083b95eb78d053a7c42100f73b39c8c79efab7d64de23f78b70ff4a9
Timestamp: 1731513656 Timestamp [UCT]: 2024-11-13 16:00:56 Age [y:d:h:m:s]: 00:134:09:20:58
Block: 1152916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95865 RingCT/type: yes/0
Extra: 01c49fcb1c083b95eb78d053a7c42100f73b39c8c79efab7d64de23f78b70ff4a9021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b667ef322cca070d9d625ac9b5a30aa2081b6296c595fa18a36179d9ada38f 0.600000000000 1638523 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": 1152926, "vin": [ { "gen": { "height": 1152916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b667ef322cca070d9d625ac9b5a30aa2081b6296c595fa18a36179d9ada38f" } } ], "extra": [ 1, 196, 159, 203, 28, 8, 59, 149, 235, 120, 208, 83, 167, 196, 33, 0, 247, 59, 57, 200, 199, 158, 250, 183, 214, 77, 226, 63, 120, 183, 15, 244, 169, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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