Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb0dbc3d6a6d7b15766808a0261cf099b6d56471373dcce3af96343e1b1ee76b

Tx prefix hash: ddb545af5c15a25f1588d52947a298db4288d05e3ae5940c23f1b0eb063fc7cb
Tx public key: bb90b7ac6948019e2eddbcc77fee593f94b3e37b6105c8a49a198365b600a4ae
Timestamp: 1726486606 Timestamp [UCT]: 2024-09-16 11:36:46 Age [y:d:h:m:s]: 00:115:00:23:52
Block: 1111335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82250 RingCT/type: yes/0
Extra: 01bb90b7ac6948019e2eddbcc77fee593f94b3e37b6105c8a49a198365b600a4ae02110000000ee914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: a987c26aba6ceef16820033bfe8a9c5bc0de05263421015fd83236958066e6c9 0.608000000000 1590254 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": 1111345, "vin": [ { "gen": { "height": 1111335 } } ], "vout": [ { "amount": 608000000, "target": { "key": "a987c26aba6ceef16820033bfe8a9c5bc0de05263421015fd83236958066e6c9" } } ], "extra": [ 1, 187, 144, 183, 172, 105, 72, 1, 158, 46, 221, 188, 199, 127, 238, 89, 63, 148, 179, 227, 123, 97, 5, 200, 164, 154, 25, 131, 101, 182, 0, 164, 174, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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