Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d562b298560a2f3962f38dff7f9a2b49bb490353893d6d9b02b41fd24f753e23

Tx prefix hash: 0d21ae3a3aa5989758f9e7dedf8a76d1be591444283050514c26ca6f7ee0ad79
Tx public key: bbf8d17a1cc693e138d6becfbc737babfd468392e68626d791369bd01d4e2e59
Timestamp: 1707563886 Timestamp [UCT]: 2024-02-10 11:18:06 Age [y:d:h:m:s]: 00:316:09:39:45
Block: 954448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226558 RingCT/type: yes/0
Extra: 01bbf8d17a1cc693e138d6becfbc737babfd468392e68626d791369bd01d4e2e590211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354b2afa68acf8cac1c28712b5ed01ea38bccf1a83e1e0490f7fb6da060daa90 0.600000000000 1413728 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": 954458, "vin": [ { "gen": { "height": 954448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354b2afa68acf8cac1c28712b5ed01ea38bccf1a83e1e0490f7fb6da060daa90" } } ], "extra": [ 1, 187, 248, 209, 122, 28, 198, 147, 225, 56, 214, 190, 207, 188, 115, 123, 171, 253, 70, 131, 146, 230, 134, 38, 215, 145, 54, 155, 208, 29, 78, 46, 89, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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