Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 567c2b397742ed1d5bb4cc7406eb1376b67e593efd71040214faf4a4ff73cb69

Tx prefix hash: 7817d274655da393b3a4dcf5932db635c1f280f1c6dd66c70a647dbd688ebf38
Tx public key: 5bedc24882d85948e2424114d9500f9ece8bc1463b6d3337f4a9e93b5e0aa9f9
Timestamp: 1724447752 Timestamp [UCT]: 2024-08-23 21:15:52 Age [y:d:h:m:s]: 00:237:16:23:51
Block: 1094451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169726 RingCT/type: yes/0
Extra: 015bedc24882d85948e2424114d9500f9ece8bc1463b6d3337f4a9e93b5e0aa9f9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace2bb36316695f8ac1dc3c40c21ede88fc39bed95e2239e7d7f1c166e39a1fd 0.600000000000 1569568 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": 1094461, "vin": [ { "gen": { "height": 1094451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace2bb36316695f8ac1dc3c40c21ede88fc39bed95e2239e7d7f1c166e39a1fd" } } ], "extra": [ 1, 91, 237, 194, 72, 130, 216, 89, 72, 226, 66, 65, 20, 217, 80, 15, 158, 206, 139, 193, 70, 59, 109, 51, 55, 244, 169, 233, 59, 94, 10, 169, 249, 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