Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c62632db34fba9fa4a17f736a2127e65d7f4f515bf876fe927566a632b08b1

Tx prefix hash: 4113094fdf8d0d97b3609e7b4a0092beeb3ebd7f1338d1ff3ae40ecb3748b436
Tx public key: 010db243104db91d9bc29b2700da9ff37bfca2c1f47ca99d4b05524f38870189
Timestamp: 1648626862 Timestamp [UCT]: 2022-03-30 07:54:22 Age [y:d:h:m:s]: 03:216:11:06:07
Block: 469435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 932688 RingCT/type: yes/0
Extra: 01010db243104db91d9bc29b2700da9ff37bfca2c1f47ca99d4b05524f3887018902110000000ac9067537000000000000000000

1 output(s) for total of 17.083121257000 dcy

stealth address amount amount idx
00: bc3a4f963d6380852b5b0fa14d4446fae91ee6c57f48a36ad9fc52d3f8d259f8 17.083121257000 888383 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": 469445, "vin": [ { "gen": { "height": 469435 } } ], "vout": [ { "amount": 17083121257, "target": { "key": "bc3a4f963d6380852b5b0fa14d4446fae91ee6c57f48a36ad9fc52d3f8d259f8" } } ], "extra": [ 1, 1, 13, 178, 67, 16, 77, 185, 29, 155, 194, 155, 39, 0, 218, 159, 243, 123, 252, 162, 193, 244, 124, 169, 157, 75, 5, 82, 79, 56, 135, 1, 137, 2, 17, 0, 0, 0, 10, 201, 6, 117, 55, 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