Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 360a9136a007f8f30269069a08c0409ba1d821880204cd4e73067f62871d93cc

Tx prefix hash: cd0c5f10b76d20a682bf47dd954aa55633306abab0b7d19a67cfcfdad9ccc372
Tx public key: d83a130488c0d76aa8d34a925a441aa5b793838d21f5dd0ef06efd813556eba2
Timestamp: 1723791256 Timestamp [UCT]: 2024-08-16 06:54:16 Age [y:d:h:m:s]: 00:227:11:42:57
Block: 1088984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162462 RingCT/type: yes/0
Extra: 01d83a130488c0d76aa8d34a925a441aa5b793838d21f5dd0ef06efd813556eba2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21262b135b7f4c1cdf7f1d5d2ce87f08d744c5b9866c3a57a89e3d903dafeab0 0.600000000000 1563603 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": 1088994, "vin": [ { "gen": { "height": 1088984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21262b135b7f4c1cdf7f1d5d2ce87f08d744c5b9866c3a57a89e3d903dafeab0" } } ], "extra": [ 1, 216, 58, 19, 4, 136, 192, 215, 106, 168, 211, 74, 146, 90, 68, 26, 165, 183, 147, 131, 141, 33, 245, 221, 14, 240, 110, 253, 129, 53, 86, 235, 162, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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