Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f908d25d6a60cd46f1bc2c914a2042d7f0983a915256d986687b29b4aa7ef98

Tx prefix hash: 99a53b83ee0bc3c2e82ad4f4df43c39d256bfff2222106008bd38c08beab25ef
Tx public key: 7eb93dfc37b6e27843ae96cb8baccab0675b141e9d2d819705b5e321140862f1
Timestamp: 1718680401 Timestamp [UCT]: 2024-06-18 03:13:21 Age [y:d:h:m:s]: 00:277:16:37:03
Block: 1046616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198434 RingCT/type: yes/0
Extra: 017eb93dfc37b6e27843ae96cb8baccab0675b141e9d2d819705b5e321140862f102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30d0466e0f97dc209ca6b801a42241a9b39d97e5af8149bd57e445e5f1db5ada 0.600000000000 1516433 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": 1046626, "vin": [ { "gen": { "height": 1046616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30d0466e0f97dc209ca6b801a42241a9b39d97e5af8149bd57e445e5f1db5ada" } } ], "extra": [ 1, 126, 185, 61, 252, 55, 182, 226, 120, 67, 174, 150, 203, 139, 172, 202, 176, 103, 91, 20, 30, 157, 45, 129, 151, 5, 181, 227, 33, 20, 8, 98, 241, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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