Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3391516d6ad1f59583c4d176738982f62498585877887a19f696fcf5dcd24d

Tx prefix hash: 18bd0679e8ccd447b14756e194df9f2041ff8b8b6b67f0374af29fd40c117869
Tx public key: e9d5f5e54f0a9afddd53119099fc4df66e924e1e094f788bf66d53ceb9becff0
Timestamp: 1719292902 Timestamp [UCT]: 2024-06-25 05:21:42 Age [y:d:h:m:s]: 00:269:01:06:21
Block: 1051685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192258 RingCT/type: yes/0
Extra: 01e9d5f5e54f0a9afddd53119099fc4df66e924e1e094f788bf66d53ceb9becff002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 390d8192067b9c30d5e8665adadee4206fa4e694a90a0cd7d1ba546ecf31ec12 0.600000000000 1522000 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": 1051695, "vin": [ { "gen": { "height": 1051685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "390d8192067b9c30d5e8665adadee4206fa4e694a90a0cd7d1ba546ecf31ec12" } } ], "extra": [ 1, 233, 213, 245, 229, 79, 10, 154, 253, 221, 83, 17, 144, 153, 252, 77, 246, 110, 146, 78, 30, 9, 79, 120, 139, 246, 109, 83, 206, 185, 190, 207, 240, 2, 17, 0, 0, 0, 6, 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