Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba2d8f0c4ab11b8a45cebb2473a9920a36255e8aaabccd9ceb3622f388858c4b

Tx prefix hash: 4ed6fc760a27b0f32ca8f5fdcf338c35300c811c1d376b7474b5e53d256a57f6
Tx public key: 33e63992312d946bdf305897823c92b25ba6492248f7f08d48dba7146d08421a
Timestamp: 1676990293 Timestamp [UCT]: 2023-02-21 14:38:13 Age [y:d:h:m:s]: 02:043:06:18:02
Block: 701867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552510 RingCT/type: yes/0
Extra: 0133e63992312d946bdf305897823c92b25ba6492248f7f08d48dba7146d08421a02110000000174b6d784000000000000000000

1 output(s) for total of 2.900168163000 dcy

stealth address amount amount idx
00: a66aa2e10e32d9e51713eaa24ae6645f65dac9ec12437d3bcfb7e025339b2f01 2.900168163000 1145358 of 0

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": 701877, "vin": [ { "gen": { "height": 701867 } } ], "vout": [ { "amount": 2900168163, "target": { "key": "a66aa2e10e32d9e51713eaa24ae6645f65dac9ec12437d3bcfb7e025339b2f01" } } ], "extra": [ 1, 51, 230, 57, 146, 49, 45, 148, 107, 223, 48, 88, 151, 130, 60, 146, 178, 91, 166, 73, 34, 72, 247, 240, 141, 72, 219, 167, 20, 109, 8, 66, 26, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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