Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f93cddc17d744f75eb0bebea46e20c556e9a902f643af89120514ba8909a1f0

Tx prefix hash: 01334df23991ea1e6f6ea2ae41bebd3cdbe8d8d7e6c5467cb8df313835a39601
Tx public key: 00fcf9b275e4b472124d04f8f72175a658e45b1364272cb4a709a4f7d743a3c5
Timestamp: 1735782492 Timestamp [UCT]: 2025-01-02 01:48:12 Age [y:d:h:m:s]: 00:349:10:41:24
Block: 1188263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247303 RingCT/type: yes/0
Extra: 0100fcf9b275e4b472124d04f8f72175a658e45b1364272cb4a709a4f7d743a3c5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e287a1fdad5d2cee19dd91a67efe1e53b4bda039a1b4defec37cfee255bb35e5 0.600000000000 1674764 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": 1188273, "vin": [ { "gen": { "height": 1188263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e287a1fdad5d2cee19dd91a67efe1e53b4bda039a1b4defec37cfee255bb35e5" } } ], "extra": [ 1, 0, 252, 249, 178, 117, 228, 180, 114, 18, 77, 4, 248, 247, 33, 117, 166, 88, 228, 91, 19, 100, 39, 44, 180, 167, 9, 164, 247, 215, 67, 163, 197, 2, 17, 0, 0, 0, 2, 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