Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cecc74433382b87cee3fc4b06d245e228eeef07cdba1cd9211e08c244d8df81

Tx prefix hash: f3a689d6347de7f7459718f0dc233d4f1c15ec9ef6ecf182ff6a879e97279933
Tx public key: 0b75f4fda677fbc73a0333f2e8dd5e61faca55bab06b419c3c6355e03fd22e38
Timestamp: 1732020510 Timestamp [UCT]: 2024-11-19 12:48:30 Age [y:d:h:m:s]: 00:133:12:57:16
Block: 1157123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95238 RingCT/type: yes/0
Extra: 010b75f4fda677fbc73a0333f2e8dd5e61faca55bab06b419c3c6355e03fd22e380211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96240b1d140948e9277edb878c47f76ad289f7d3aa256c383687997a39ce4c0 0.600000000000 1642746 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": 1157133, "vin": [ { "gen": { "height": 1157123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96240b1d140948e9277edb878c47f76ad289f7d3aa256c383687997a39ce4c0" } } ], "extra": [ 1, 11, 117, 244, 253, 166, 119, 251, 199, 58, 3, 51, 242, 232, 221, 94, 97, 250, 202, 85, 186, 176, 107, 65, 156, 60, 99, 85, 224, 63, 210, 46, 56, 2, 17, 0, 0, 0, 3, 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