Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac58472b8cb71350676b31b6da91e48da087cc3ef95be6e8817cdab0d655c4d3

Tx prefix hash: 5042292c212fea4d2d6706e84fff902666d8d4888a76508ecf45d386cf3c2d01
Tx public key: a5af7d06e670e341a7788e50a0cc4191ed9347b03a77bddafbe2b471b0bc9f5d
Timestamp: 1728320785 Timestamp [UCT]: 2024-10-07 17:06:25 Age [y:d:h:m:s]: 00:157:22:17:57
Block: 1126536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112670 RingCT/type: yes/0
Extra: 01a5af7d06e670e341a7788e50a0cc4191ed9347b03a77bddafbe2b471b0bc9f5d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fd66592f9f2153504a3355f0309afccdb8111fbe85c3e5723b9ff09e0d0004f 0.600000000000 1609331 of 15

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": 1126546, "vin": [ { "gen": { "height": 1126536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fd66592f9f2153504a3355f0309afccdb8111fbe85c3e5723b9ff09e0d0004f" } } ], "extra": [ 1, 165, 175, 125, 6, 230, 112, 227, 65, 167, 120, 142, 80, 160, 204, 65, 145, 237, 147, 71, 176, 58, 119, 189, 218, 251, 226, 180, 113, 176, 188, 159, 93, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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