Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23e8e2f947e04f3bdd3405601fe1609525e0aecc3de682152d127c9dcf19780

Tx prefix hash: 6a957879241728037dccb82f7dbf2e16fbbe056d743deb3443a97e3b8a08e027
Tx public key: 05369b2aed0e8fb4ffc1ea38ec792840a0134bf69891d13ae03fcdfa6805299f
Timestamp: 1634783528 Timestamp [UCT]: 2021-10-21 02:32:08 Age [y:d:h:m:s]: 03:145:12:43:54
Block: 357159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 882043 RingCT/type: yes/0
Extra: 0105369b2aed0e8fb4ffc1ea38ec792840a0134bf69891d13ae03fcdfa6805299f02110000000a36fe6557000000000000000000

1 output(s) for total of 40.233182049000 dcy

stealth address amount amount idx
00: a6fccdcccc320508f41f3423d3741a1c85d61542fdf7acac1b57b20d9daa91fe 40.233182049000 728393 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": 357169, "vin": [ { "gen": { "height": 357159 } } ], "vout": [ { "amount": 40233182049, "target": { "key": "a6fccdcccc320508f41f3423d3741a1c85d61542fdf7acac1b57b20d9daa91fe" } } ], "extra": [ 1, 5, 54, 155, 42, 237, 14, 143, 180, 255, 193, 234, 56, 236, 121, 40, 64, 160, 19, 75, 246, 152, 145, 209, 58, 224, 63, 205, 250, 104, 5, 41, 159, 2, 17, 0, 0, 0, 10, 54, 254, 101, 87, 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