Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2706dfdf899d49c03a808202c14a262450d6d0860d2059f090d7f88b7db79fc6

Tx prefix hash: 0c5bcccec8746cb15ce96271f5e30a78336e484bbdfb510b245d989c741022de
Tx public key: 6865a932f58b6a0252f5917f60686eb24cb84c50f6e4e6cfa013fc84c1d10fb7
Timestamp: 1722888121 Timestamp [UCT]: 2024-08-05 20:02:01 Age [y:d:h:m:s]: 00:247:08:19:38
Block: 1081501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176675 RingCT/type: yes/0
Extra: 016865a932f58b6a0252f5917f60686eb24cb84c50f6e4e6cfa013fc84c1d10fb702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eedeffddc3e6c1d8688744a11aa671f5f037954ef2431656e22cde363854925 0.600000000000 1555270 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": 1081511, "vin": [ { "gen": { "height": 1081501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eedeffddc3e6c1d8688744a11aa671f5f037954ef2431656e22cde363854925" } } ], "extra": [ 1, 104, 101, 169, 50, 245, 139, 106, 2, 82, 245, 145, 127, 96, 104, 110, 178, 76, 184, 76, 80, 246, 228, 230, 207, 160, 19, 252, 132, 193, 209, 15, 183, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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