Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b55c120f790747eb7feebd2d7c05d141b375655441d9707d08e63a730024e58

Tx prefix hash: c27a6885858848e9f0171d18525623c34fab645cbc030de832d64c1a9afd4ab4
Tx public key: 2dae0091a9e272a1f4ce56deeff8c3ec2fe1d5999c57271209ce4032c513c620
Timestamp: 1673584177 Timestamp [UCT]: 2023-01-13 04:29:37 Age [y:d:h:m:s]: 02:030:22:09:32
Block: 673610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543745 RingCT/type: yes/0
Extra: 012dae0091a9e272a1f4ce56deeff8c3ec2fe1d5999c57271209ce4032c513c62002110000000175e3f0e9000000000000000000

1 output(s) for total of 3.597910809000 dcy

stealth address amount amount idx
00: 26e7a91e6995916f89c23ef3ddb29d40e8dfe61294c7d30e9d1d6c8edcf3fb98 3.597910809000 1115225 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": 673620, "vin": [ { "gen": { "height": 673610 } } ], "vout": [ { "amount": 3597910809, "target": { "key": "26e7a91e6995916f89c23ef3ddb29d40e8dfe61294c7d30e9d1d6c8edcf3fb98" } } ], "extra": [ 1, 45, 174, 0, 145, 169, 226, 114, 161, 244, 206, 86, 222, 239, 248, 195, 236, 47, 225, 213, 153, 156, 87, 39, 18, 9, 206, 64, 50, 197, 19, 198, 32, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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