Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050f2e537edaf8df54a7bfdb333791ea29c58e0f68f2cc97e53e716f0c6eaf4c

Tx prefix hash: f2d8b12e179877b9a83f1b7ac198afa17e40b80922e4e81a5cd78f8060e78e11
Tx public key: 5777be55e29a7209636235748c2d0a2c7248efedad8225f95731bfae0e03c060
Timestamp: 1729432043 Timestamp [UCT]: 2024-10-20 13:47:23 Age [y:d:h:m:s]: 00:076:00:11:10
Block: 1135736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54335 RingCT/type: yes/0
Extra: 015777be55e29a7209636235748c2d0a2c7248efedad8225f95731bfae0e03c0600211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e228554202437b0d5d86e01738886c35e5ee5edc39a2bf11c596cbdf3bead2 0.600000000000 1619075 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": 1135746, "vin": [ { "gen": { "height": 1135736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e228554202437b0d5d86e01738886c35e5ee5edc39a2bf11c596cbdf3bead2" } } ], "extra": [ 1, 87, 119, 190, 85, 226, 154, 114, 9, 99, 98, 53, 116, 140, 45, 10, 44, 114, 72, 239, 237, 173, 130, 37, 249, 87, 49, 191, 174, 14, 3, 192, 96, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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