Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe16d34eb0c4cd0edc65d97276257b465151cf1ed178068c131741dad0946075

Tx prefix hash: 0660c5f3fb337f367bbac53b72c82ba0c1d54b089ab3abd173f520da25566a3a
Tx public key: 724c8ff425a1c57c7d5040f92bbd5bcf1fb678c472699160ac238b8b52e43b65
Timestamp: 1681006876 Timestamp [UCT]: 2023-04-09 02:21:16 Age [y:d:h:m:s]: 01:361:09:52:18
Block: 734579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519535 RingCT/type: yes/0
Extra: 01724c8ff425a1c57c7d5040f92bbd5bcf1fb678c472699160ac238b8b52e43b650211000000035029cbac000000000000000000

1 output(s) for total of 2.259618181000 dcy

stealth address amount amount idx
00: f3699bee9a05e9fdcbc84e3c0a25a8f13f61139a2fa64128103b1baad6f148d0 2.259618181000 1180806 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": 734589, "vin": [ { "gen": { "height": 734579 } } ], "vout": [ { "amount": 2259618181, "target": { "key": "f3699bee9a05e9fdcbc84e3c0a25a8f13f61139a2fa64128103b1baad6f148d0" } } ], "extra": [ 1, 114, 76, 143, 244, 37, 161, 197, 124, 125, 80, 64, 249, 43, 189, 91, 207, 31, 182, 120, 196, 114, 105, 145, 96, 172, 35, 139, 139, 82, 228, 59, 101, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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