Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2290bf8a5f4d0bec0d71ec33304e6cd2a6219a57fb06da9e5150da0b6d2043c

Tx prefix hash: 242047c6d5534a44cd184caaaed24490facda4a0211869e871d245862633f1fd
Tx public key: 51526ec3d0e7f294ff61241aba40238bf2f965572a8f64a8e729daa2b0606083
Timestamp: 1707761659 Timestamp [UCT]: 2024-02-12 18:14:19 Age [y:d:h:m:s]: 01:128:00:49:04
Block: 956091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352462 RingCT/type: yes/0
Extra: 0151526ec3d0e7f294ff61241aba40238bf2f965572a8f64a8e729daa2b060608302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e679a7fb47d05383a793e1061fc8fc412ecaf965c7cd0a42efca9ca653282a0 0.600000000000 1415393 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": 956101, "vin": [ { "gen": { "height": 956091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e679a7fb47d05383a793e1061fc8fc412ecaf965c7cd0a42efca9ca653282a0" } } ], "extra": [ 1, 81, 82, 110, 195, 208, 231, 242, 148, 255, 97, 36, 26, 186, 64, 35, 139, 242, 249, 101, 87, 42, 143, 100, 168, 231, 41, 218, 162, 176, 96, 96, 131, 2, 17, 0, 0, 0, 3, 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