Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abaa69188b352422d7292761d47ce2015c8542c6f8b5832f9cc9568b1f138525

Tx prefix hash: c8376ad79b57a09e52a934f77248b62d54fe8f6274994246e47e495fc4a48c0a
Tx public key: f7d20771718e3335484e9448ae9c95571b7457c9c60218e1324c7c40e53b8f0e
Timestamp: 1736249745 Timestamp [UCT]: 2025-01-07 11:35:45 Age [y:d:h:m:s]: 00:071:00:04:22
Block: 1192130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50546 RingCT/type: yes/0
Extra: 01f7d20771718e3335484e9448ae9c95571b7457c9c60218e1324c7c40e53b8f0e02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 491d1b06d78f09f28d7d648bd5aa5c9f2af3f9d278a8467583e574678347ba7a 0.600000000000 1678677 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": 1192140, "vin": [ { "gen": { "height": 1192130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "491d1b06d78f09f28d7d648bd5aa5c9f2af3f9d278a8467583e574678347ba7a" } } ], "extra": [ 1, 247, 210, 7, 113, 113, 142, 51, 53, 72, 78, 148, 72, 174, 156, 149, 87, 27, 116, 87, 201, 198, 2, 24, 225, 50, 76, 124, 64, 229, 59, 143, 14, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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