Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f870fdf08cef32133079d51dd5c5713d94877e220af84cf4ec10b5d70f76dc

Tx prefix hash: f9ab1b3962eb076c315a0ea1aebbffa9bd3e30e3079e4ef8d70989e296ee2c1a
Tx public key: 961b42566f573fd643f0e7bf72095aa664f7f12b2ff2bb0a6b005e4a5707f669
Timestamp: 1659970166 Timestamp [UCT]: 2022-08-08 14:49:26 Age [y:d:h:m:s]: 02:227:18:38:55
Block: 561478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683979 RingCT/type: yes/0
Extra: 01961b42566f573fd643f0e7bf72095aa664f7f12b2ff2bb0a6b005e4a5707f66902110000000124ffc81c000000000000000000

1 output(s) for total of 8.464287784000 dcy

stealth address amount amount idx
00: 415a31026755d715fb57ad0dde4fb7cafe65318f9aa1cb73950b251bfa1a547a 8.464287784000 993818 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": 561488, "vin": [ { "gen": { "height": 561478 } } ], "vout": [ { "amount": 8464287784, "target": { "key": "415a31026755d715fb57ad0dde4fb7cafe65318f9aa1cb73950b251bfa1a547a" } } ], "extra": [ 1, 150, 27, 66, 86, 111, 87, 63, 214, 67, 240, 231, 191, 114, 9, 90, 166, 100, 247, 241, 43, 47, 242, 187, 10, 107, 0, 94, 74, 87, 7, 246, 105, 2, 17, 0, 0, 0, 1, 36, 255, 200, 28, 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