Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7c9962a65252bd272fae408c7edacf6acd60dc50df5fdce8b8a0de8b340ba0d

Tx prefix hash: bdeb614679c8eb9d4c2c02f52f95a6a613ec64af046864dc1c67137cfc38c7a2
Tx public key: 5775734b81dd3f4e2d28de694c5d1a463fbae5d63ec5aaa571fdde84e7ac6b96
Timestamp: 1714668118 Timestamp [UCT]: 2024-05-02 16:41:58 Age [y:d:h:m:s]: 00:206:06:04:42
Block: 1013356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147641 RingCT/type: yes/0
Extra: 015775734b81dd3f4e2d28de694c5d1a463fbae5d63ec5aaa571fdde84e7ac6b960211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a78e57a46743acf9fc706453ad7b78f9578dea427b5579541001fa81cb61533 0.600000000000 1476151 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": 1013366, "vin": [ { "gen": { "height": 1013356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a78e57a46743acf9fc706453ad7b78f9578dea427b5579541001fa81cb61533" } } ], "extra": [ 1, 87, 117, 115, 75, 129, 221, 63, 78, 45, 40, 222, 105, 76, 93, 26, 70, 63, 186, 229, 214, 62, 197, 170, 165, 113, 253, 222, 132, 231, 172, 107, 150, 2, 17, 0, 0, 0, 4, 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