Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 895341a8845e86a877b4140c1bb09329337c8cbb729647a8c3633f6731063e17

Tx prefix hash: b4abf0b230fb23310429cb137aae6cfd13cdf1c171f4046d75d3e967fc45d0b1
Tx public key: ff89187c48dd2c0e9242dbda5f9b7caf4f640f3b1f41ac60976dd86e6b8fbed8
Timestamp: 1721555369 Timestamp [UCT]: 2024-07-21 09:49:29 Age [y:d:h:m:s]: 00:284:00:40:35
Block: 1070439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202931 RingCT/type: yes/0
Extra: 01ff89187c48dd2c0e9242dbda5f9b7caf4f640f3b1f41ac60976dd86e6b8fbed802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cbebf18d4e08373140987b3fcb2810fb8d10b092011be46e255ae91cb13229b 0.600000000000 1542276 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": 1070449, "vin": [ { "gen": { "height": 1070439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cbebf18d4e08373140987b3fcb2810fb8d10b092011be46e255ae91cb13229b" } } ], "extra": [ 1, 255, 137, 24, 124, 72, 221, 44, 14, 146, 66, 219, 218, 95, 155, 124, 175, 79, 100, 15, 59, 31, 65, 172, 96, 151, 109, 216, 110, 107, 143, 190, 216, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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