Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aacad69a1a03606daf2ad344f3a0ffb39b4d5a05b324e63a9084b26306339d6b

Tx prefix hash: f5a0a247833c2d0f28d96f9c23b5486b4d7aa30c6e1b5cb7c9fe5f98dd91b638
Tx public key: af55233010ca68f5813b195e23852a7b390793ebb783126c0364fa1f8865737f
Timestamp: 1664483138 Timestamp [UCT]: 2022-09-29 20:25:38 Age [y:d:h:m:s]: 02:190:01:10:11
Block: 598420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 657389 RingCT/type: yes/0
Extra: 01af55233010ca68f5813b195e23852a7b390793ebb783126c0364fa1f8865737f02110000000133af99f4000000000000000000

1 output(s) for total of 6.385371744000 dcy

stealth address amount amount idx
00: 89e739fae44c7940c8f556daa58d9b39d9fd90c2d6f16d12c33b72c2adf72c61 6.385371744000 1034175 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": 598430, "vin": [ { "gen": { "height": 598420 } } ], "vout": [ { "amount": 6385371744, "target": { "key": "89e739fae44c7940c8f556daa58d9b39d9fd90c2d6f16d12c33b72c2adf72c61" } } ], "extra": [ 1, 175, 85, 35, 48, 16, 202, 104, 245, 129, 59, 25, 94, 35, 133, 42, 123, 57, 7, 147, 235, 183, 131, 18, 108, 3, 100, 250, 31, 136, 101, 115, 127, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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