Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84aa32147bd121d84d5339da3f40cd2e7d2f3c1bc8884feda91e43a0c1741a39

Tx prefix hash: 30b16eede6a3d789884b9623e2b4360feda8ee20201571b231dc8ccafbdee300
Tx public key: d1ed9abb98db7c9dbf8cb17742eca0a1dc6af535193d466c0c7f829a44df891f
Timestamp: 1730718434 Timestamp [UCT]: 2024-11-04 11:07:14 Age [y:d:h:m:s]: 00:138:11:41:03
Block: 1146316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98832 RingCT/type: yes/0
Extra: 01d1ed9abb98db7c9dbf8cb17742eca0a1dc6af535193d466c0c7f829a44df891f021100000001ca365e8f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18712201298612412b05b66c78e4914f9fc8c7d7376160bd46c8e640834212bd 0.600000000000 1630933 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": 1146326, "vin": [ { "gen": { "height": 1146316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18712201298612412b05b66c78e4914f9fc8c7d7376160bd46c8e640834212bd" } } ], "extra": [ 1, 209, 237, 154, 187, 152, 219, 124, 157, 191, 140, 177, 119, 66, 236, 160, 161, 220, 106, 245, 53, 25, 61, 70, 108, 12, 127, 130, 154, 68, 223, 137, 31, 2, 17, 0, 0, 0, 1, 202, 54, 94, 143, 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