Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57c5c84f1b8b4a515d2e15db98ea45e383a033530b18fb0d8028cb2facdc98a

Tx prefix hash: 7b12a2dc5e851686c7d0ca5ac9425baa8530fdb34939ff07c57625005ab2445a
Tx public key: f558f9e309beb2e92d939417953762c0d0a9ed6873648f8c8e880d0a9271cb70
Timestamp: 1704787296 Timestamp [UCT]: 2024-01-09 08:01:36 Age [y:d:h:m:s]: 01:305:20:10:37
Block: 931413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477420 RingCT/type: yes/0
Extra: 01f558f9e309beb2e92d939417953762c0d0a9ed6873648f8c8e880d0a9271cb700211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7fe23bd65d2b0091537d108892871205b0b59d178dcd9bbaf86da81342e3003 0.600000000000 1389311 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": 931423, "vin": [ { "gen": { "height": 931413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7fe23bd65d2b0091537d108892871205b0b59d178dcd9bbaf86da81342e3003" } } ], "extra": [ 1, 245, 88, 249, 227, 9, 190, 178, 233, 45, 147, 148, 23, 149, 55, 98, 192, 208, 169, 237, 104, 115, 100, 143, 140, 142, 136, 13, 10, 146, 113, 203, 112, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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