Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ef67a3cae3d54be40a70cb0ed07a391e1f3837cfbc3f73c668005224e38b5f

Tx prefix hash: 4b513a62bf476d605bbf213dabefbbdbb409548c9e9cb0afeff6672e40c3f1d9
Tx public key: d339fbb21f47a3f0511f2d72540f7bbea2a9e31d233aa01c79539690746ca8b9
Timestamp: 1708875795 Timestamp [UCT]: 2024-02-25 15:43:15 Age [y:d:h:m:s]: 01:029:18:06:44
Block: 965338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282262 RingCT/type: yes/0
Extra: 01d339fbb21f47a3f0511f2d72540f7bbea2a9e31d233aa01c79539690746ca8b90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ac2d0470016c5b1e927b2233373427b7797641eaa2aac78299cff86b73a741 0.600000000000 1425089 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": 965348, "vin": [ { "gen": { "height": 965338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ac2d0470016c5b1e927b2233373427b7797641eaa2aac78299cff86b73a741" } } ], "extra": [ 1, 211, 57, 251, 178, 31, 71, 163, 240, 81, 31, 45, 114, 84, 15, 123, 190, 162, 169, 227, 29, 35, 58, 160, 28, 121, 83, 150, 144, 116, 108, 168, 185, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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