Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a3739b97072bc7b4b2ccfe138be9b023106c493f879108a54f65c2af087f75

Tx prefix hash: 2cd842f97f8b5cc0d4b8f4d96fdf02be839435a7c9754548ed8d7ff39d7ff0b2
Tx public key: e611cb92084e71e7d7ba2696d471cd8ec9112ecf05748009333fc781556043a7
Timestamp: 1682553951 Timestamp [UCT]: 2023-04-27 00:05:51 Age [y:d:h:m:s]: 02:033:08:39:16
Block: 747360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546015 RingCT/type: yes/0
Extra: 01e611cb92084e71e7d7ba2696d471cd8ec9112ecf05748009333fc781556043a702110000000333af99f4000000000000000000

1 output(s) for total of 2.049681037000 dcy

stealth address amount amount idx
00: 7e702271f6a874314940a0d30627c116e8796a1a21f613edf7e591b687162f4a 2.049681037000 1195019 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": 747370, "vin": [ { "gen": { "height": 747360 } } ], "vout": [ { "amount": 2049681037, "target": { "key": "7e702271f6a874314940a0d30627c116e8796a1a21f613edf7e591b687162f4a" } } ], "extra": [ 1, 230, 17, 203, 146, 8, 78, 113, 231, 215, 186, 38, 150, 212, 113, 205, 142, 201, 17, 46, 207, 5, 116, 128, 9, 51, 63, 199, 129, 85, 96, 67, 167, 2, 17, 0, 0, 0, 3, 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