Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb64d1460962800176b8d5d84e136346e666a4119c64429bc050abbea81bc7e4

Tx prefix hash: aeef0c285bf87b32ce0979d9059731d2d60d0b5121e828704f6d62b7fa18cc62
Tx public key: be37a60bf243b1c5a7344c9940d8d96109568333c8b3283fb77e401395ae0e9d
Timestamp: 1714239631 Timestamp [UCT]: 2024-04-27 17:40:31 Age [y:d:h:m:s]: 00:270:16:04:07
Block: 1009798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193680 RingCT/type: yes/0
Extra: 01be37a60bf243b1c5a7344c9940d8d96109568333c8b3283fb77e401395ae0e9d02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a379918e14899998c5a1915c22fa2e8bb5ab19d79f3321ffcb271151e54540e 0.600000000000 1471570 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": 1009808, "vin": [ { "gen": { "height": 1009798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a379918e14899998c5a1915c22fa2e8bb5ab19d79f3321ffcb271151e54540e" } } ], "extra": [ 1, 190, 55, 166, 11, 242, 67, 177, 197, 167, 52, 76, 153, 64, 216, 217, 97, 9, 86, 131, 51, 200, 179, 40, 63, 183, 126, 64, 19, 149, 174, 14, 157, 2, 17, 0, 0, 0, 10, 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