Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7057b366073fb9c85377cde44f3d50e6ec0c816a847b8339240d482112b0cfa

Tx prefix hash: d9959eb4b52caca941ef3feb7b0e58b11475de4eb545acf51017fe3f914097bf
Tx public key: ddd5e5e4268db6470a412ad950cc664a2366c86b21cc3d6d07b7d044a1cbd33a
Timestamp: 1727030285 Timestamp [UCT]: 2024-09-22 18:38:05 Age [y:d:h:m:s]: 01:016:20:11:56
Block: 1115839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270394 RingCT/type: yes/0
Extra: 01ddd5e5e4268db6470a412ad950cc664a2366c86b21cc3d6d07b7d044a1cbd33a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641e12fb078634fd2c19becfd97bacdeee5a994defd3ae716f00710ec179c878 0.600000000000 1596112 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": 1115849, "vin": [ { "gen": { "height": 1115839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641e12fb078634fd2c19becfd97bacdeee5a994defd3ae716f00710ec179c878" } } ], "extra": [ 1, 221, 213, 229, 228, 38, 141, 182, 71, 10, 65, 42, 217, 80, 204, 102, 74, 35, 102, 200, 107, 33, 204, 61, 109, 7, 183, 208, 68, 161, 203, 211, 58, 2, 17, 0, 0, 0, 9, 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