Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 244c198fc2c1e91d4edae71364d9766cab8112d312542847c9f27e3fb10c142a

Tx prefix hash: 2ac963f8876af1984ba86ae532ad74e076fbebc2713c4c68926ad268f8007036
Tx public key: 02b3b39c0d7ef23475f05d89d095d5615f75b59492deb3616d403138f04fd7fd
Timestamp: 1682532570 Timestamp [UCT]: 2023-04-26 18:09:30 Age [y:d:h:m:s]: 01:208:18:07:44
Block: 747178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410630 RingCT/type: yes/0
Extra: 0102b3b39c0d7ef23475f05d89d095d5615f75b59492deb3616d403138f04fd7fd0211000000027e406890000000000000000000

1 output(s) for total of 2.052529109000 dcy

stealth address amount amount idx
00: d9409fbf224ac34bea3bd7ab802196dcc155b156882b99d7858029a25a513e63 2.052529109000 1194823 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": 747188, "vin": [ { "gen": { "height": 747178 } } ], "vout": [ { "amount": 2052529109, "target": { "key": "d9409fbf224ac34bea3bd7ab802196dcc155b156882b99d7858029a25a513e63" } } ], "extra": [ 1, 2, 179, 179, 156, 13, 126, 242, 52, 117, 240, 93, 137, 208, 149, 213, 97, 95, 117, 181, 148, 146, 222, 179, 97, 109, 64, 49, 56, 240, 79, 215, 253, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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