Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8464cb658d3c8cce0981a8185054c47c7d58a787811fabda1208e91ec97080a4

Tx prefix hash: a07fa132593d811d9e950af92a5eea0c05d9a1507a6b99676b861b63e7237c5a
Tx public key: 1b7a98023b79a9840e4f0c3f1e8692925530b38c9d8acfedacea9469837ae923
Timestamp: 1731382814 Timestamp [UCT]: 2024-11-12 03:40:14 Age [y:d:h:m:s]: 00:142:10:38:34
Block: 1151829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101630 RingCT/type: yes/0
Extra: 011b7a98023b79a9840e4f0c3f1e8692925530b38c9d8acfedacea9469837ae9230211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 973eb584f6952840f281daa9fc20063a6d44c6e0f355f6873e651cdfaa1100c3 0.600000000000 1637412 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": 1151839, "vin": [ { "gen": { "height": 1151829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "973eb584f6952840f281daa9fc20063a6d44c6e0f355f6873e651cdfaa1100c3" } } ], "extra": [ 1, 27, 122, 152, 2, 59, 121, 169, 132, 14, 79, 12, 63, 30, 134, 146, 146, 85, 48, 179, 140, 157, 138, 207, 237, 172, 234, 148, 105, 131, 122, 233, 35, 2, 17, 0, 0, 0, 1, 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