Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edaa3de296c8a4b0bb354743786dfc4118c435d5d5b28a1ca0433959f06e82de

Tx prefix hash: 083b9694f8b3b566906d99aed79f3de33d984bf614e5a2d0a0600bc3f0991a9c
Tx public key: 09298edbc73a9d3be12ae5e14253b14059f536b53c65df734e48d0622429ec72
Timestamp: 1727974336 Timestamp [UCT]: 2024-10-03 16:52:16 Age [y:d:h:m:s]: 01:035:04:01:59
Block: 1123670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283515 RingCT/type: yes/0
Extra: 0109298edbc73a9d3be12ae5e14253b14059f536b53c65df734e48d0622429ec72021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c24cfb1a59b1deffef131a9e04323f473c94e32d90b1a641cf5e54a5151a2a 0.600000000000 1606205 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": 1123680, "vin": [ { "gen": { "height": 1123670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c24cfb1a59b1deffef131a9e04323f473c94e32d90b1a641cf5e54a5151a2a" } } ], "extra": [ 1, 9, 41, 142, 219, 199, 58, 157, 59, 225, 42, 229, 225, 66, 83, 177, 64, 89, 245, 54, 181, 60, 101, 223, 115, 78, 72, 208, 98, 36, 41, 236, 114, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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