Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 195bd109df540caa42558063c869e67ac84162c26dafbb18229abe0a58db7034

Tx prefix hash: a3b80d5fb5cafb35c7e9f31ea4bfa6aa5130ae5793578dbe54093f2d019f6338
Tx public key: e65ccb71e9dd4d259317135121dd1d7f8b9dd09a86c246910577c3926b8907e7
Timestamp: 1699846170 Timestamp [UCT]: 2023-11-13 03:29:30 Age [y:d:h:m:s]: 01:362:18:11:51
Block: 890476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518162 RingCT/type: yes/0
Extra: 01e65ccb71e9dd4d259317135121dd1d7f8b9dd09a86c246910577c3926b8907e7021100000007faf35c9c000000000000000000

1 output(s) for total of 0.687833550000 dcy

stealth address amount amount idx
00: 9172e592610f78b8dedef119e944f062be8acc379e00ccecc73c595c5d943f00 0.687833550000 1346499 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": 890486, "vin": [ { "gen": { "height": 890476 } } ], "vout": [ { "amount": 687833550, "target": { "key": "9172e592610f78b8dedef119e944f062be8acc379e00ccecc73c595c5d943f00" } } ], "extra": [ 1, 230, 92, 203, 113, 233, 221, 77, 37, 147, 23, 19, 81, 33, 221, 29, 127, 139, 157, 208, 154, 134, 194, 70, 145, 5, 119, 195, 146, 107, 137, 7, 231, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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