Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d423947144e672574f0eaa1fc3a6318035131af7be749f3662938f173e230e

Tx prefix hash: 9b37ea30b67da9b5679a315162d5eeef0cf015add4fc0d474e5f123a67391a40
Tx public key: e0c230f528e532f9e2e1f7c5ddeef7ef36951a8408cf7aab7e15f783fa00a0c6
Timestamp: 1716805262 Timestamp [UCT]: 2024-05-27 10:21:02 Age [y:d:h:m:s]: 00:340:10:14:16
Block: 1031091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243294 RingCT/type: yes/0
Extra: 01e0c230f528e532f9e2e1f7c5ddeef7ef36951a8408cf7aab7e15f783fa00a0c60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8346713ed4758da79cbe9710a4dadb9f59fb85f28d28403f554f6064dd2c1fc9 0.600000000000 1499446 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": 1031101, "vin": [ { "gen": { "height": 1031091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8346713ed4758da79cbe9710a4dadb9f59fb85f28d28403f554f6064dd2c1fc9" } } ], "extra": [ 1, 224, 194, 48, 245, 40, 229, 50, 249, 226, 225, 247, 197, 221, 238, 247, 239, 54, 149, 26, 132, 8, 207, 122, 171, 126, 21, 247, 131, 250, 0, 160, 198, 2, 17, 0, 0, 0, 1, 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